-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding log binning option for source density #679
Conversation
Codecov Report
@@ Coverage Diff @@
## master #679 +/- ##
==========================================
- Coverage 42.85% 42.80% -0.05%
==========================================
Files 98 98
Lines 9443 9454 +11
==========================================
Hits 4047 4047
- Misses 5396 5407 +11
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. I feel some documentation would be good to advertise to users that there is the option of linear/log source density spacings. Would this be possible/"easy"?
sure! can do this morning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to have docs!
Link test failed due to a timeout - checked manually and this link is fine. Will merge. |
Addressing #651, I am working on enabling log binning in source density. This involves including an additional source density parameter in the beast_settings file (will update the beast-examples/ files as well), called "sd_binmode" which can be "linear" or "log". I also added raised errors for the linear case if both the number of bins and the bin width are set, and errors for the log case if the number of bins is not set.
Currently, the way it works is to find the min and max source densities in the field, and then use the sd_Nbins (number of bins) parameter to determine logarithmically-spaced bins. The minimum is the first value in the image greater than zero (as the sd image contains a lot of zeros on the edges which aren't actually from the data). Looking forward to thoughts!